-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubetest: specify kind node image and update stable version #14477
Conversation
/assign @BenTheElder @neolit123 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is cool, thanks!
I have some minor concern about trying to support every version, as kind does not yet supply a 100% stable CLI interface, we have some minor logging related changes in HEAD vs the last release currently...
kubetest/kind/kind.go
Outdated
kindClusterName = flag.String("kind-cluster-name", kindClusterNameDefault, | ||
"(kind only) Name of the kind cluster.") | ||
kindNodeImage = flag.String("kind-node-image", kindNodeImageLatest, "(kind only) name:tag of the node image to start the cluster") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably default to "" instead, and if we built then it should be replaced with what we built and if not then the kind flag should be unset.
If the flag is actually set, directly pass it through.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for your suggestion! I've updated the PR.
It might be best to just update the default version to v0.5.1 |
385281d
to
eb36bc9
Compare
eb36bc9
to
1efc3d9
Compare
done |
if buildNodeImage != "" { | ||
args = append(args, "--image="+buildNodeImage) | ||
// override user-specified node image | ||
d.kindNodeImage = buildNodeImage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I override the node image with kindNodeImageLatest
when the build is enabled, because I think it will confuse the user to start a cluster with kindest/node:v1.15.0
but it might not be kindest/node:v1.15.0
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm not sure what to do here. long term i'd like to reccomend not using kubetest for using kind.
/hold |
1efc3d9
to
067c67b
Compare
/hold cancel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
@BenTheElder what do you think? |
@BenTheElder any concerns? |
I'm going to defer to @neolit123 |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, cofyc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
i think the PR is mostly fine, yet i think kubetest/kind might be getting deprecated. there might be some users of this deployer out there, but using kind without kubetest should be preferred:
+1 |
--build
skipped) to test third-party projects, e.g. operators.build
requires kind sourcestable
uses hard-code version, however,0.2.0
is too old to use.I think it's convenient to specify kind binary version to download here without breaking anything.updated to use latest stable versionv0.5.1